home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
e
/
misc.txt
/
000021_scottac@nb.sympatico.ca_Thu Nov 9 10:46:47 2006.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Path: reader2.panix.com!reader1.panix.com!panix!logbridge.uoregon.edu!hammer.uoregon.edu!News.Dal.Ca!ursa-nb00s0.nbnet.nb.ca!53ab2750!not-for-mail
From: "Scott Caissie" <scottac@nb.sympatico.ca>
Newsgroups: comp.protocols.kermit.misc
References: <EGr4h.16408$cz.264817@ursa-nb00s0.nbnet.nb.ca> <slrnel4ma5.lfs.fdc@panix2.panix.com>
Subject: Re: SSH Timeout help
Lines: 35
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <HnA4h.16633$cz.268476@ursa-nb00s0.nbnet.nb.ca>
Date: Thu, 09 Nov 2006 07:01:59 GMT
NNTP-Posting-Host: 142.167.32.152
X-Complaints-To: abuse@aliant.net
X-Trace: ursa-nb00s0.nbnet.nb.ca 1163055719 142.167.32.152 (Thu, 09 Nov 2006 03:01:59 AST)
NNTP-Posting-Date: Thu, 09 Nov 2006 03:01:59 AST
Organization: Aliant Internet
Xref: panix comp.protocols.kermit.misc:15591
The 1 hour issue is what we're trying to track down. Didn't occur until we
upgraded the logon security.
We've got a number of clues from various tests. Could be network, or server,
related and not Kermit as a client related.
Relavent commands we have so far that worked fine before:
Set Terminal Idle-Timeout 0
Set Terminal Idle-Action Return
But this feedback does help eliminate K95 as the cause. But if so, then
perhaps the patch fix won't help in this regard.
- Scott
"Frank Da Cruz" <fdc@panix.com> wrote in message
news:slrnel4ma5.lfs.fdc@panix2.panix.com...
> On 2006-11-08, Scott Caissie <scottac@nb.sympatico.ca> wrote:
> : We just moved over to SSH. Using K95 2.1.3.
> : We are now suddenly having issues with idle timeouts. Specifically 1
> hour.
> : Times you out even on active sessions.
> :
> Addressing this one sepately... Who/what is closing the session?
> Obviously
> it's not Kermit. It's either the host you're ssh'd to, or it's a NAT or
> router or somesuch in between. I use K95 SSH all day every day and have
> never
> seen a problem like this, but then I'm not dealing with firewalls or NATs
> either. You should begin by finding out where this 1-hour timer is set.
> Maybe the place where this occurs does not care if the session is idle,
> it's simply an elapsed-time limit on the session. But it's not in Kermit.
>
> - Frank
>